IRIX Base Documentation 1998 November/IRIX 6.5.2 Base Documentation November 1998.img/usr/share/catman/u_man/cat1/mail_att.z/mail_att

Text File | 1998-10-20 | 11KB | 331 lines

MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))                                                        MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))



NNNNAAAAMMMMEEEE
     mail - send mail to users or read mail

SSSSYYYYNNNNOOOOPPPPSSSSIIIISSSS
     _S_e_n_d_i_n_g _m_a_i_l:

     mmmmaaaaiiiillll _a_d_d_r_e_s_s [ _a_d_d_r_e_s_s... ]

     _R_e_a_d_i_n_g _m_a_i_l:

     mmmmaaaaiiiillll [ ----eeeehhhhppppqqqqrrrr ] [ ----ffff _f_i_l_e ]

DDDDEEEESSSSCCCCRRRRIIIIPPPPTTTTIIIIOOOONNNN
   SSSSeeeennnnddddiiiinnnngggg MMMMaaaaiiiillll
     The command-line arguments that follow affect SENDING mail:

     An _a_d_d_r_e_s_s can be any one of the following:

     1) An RFC 822-compliant address specification (i.e.
        ``[e-mail]'').

     2) A UUCP route (i.e. ``host1!host2!user'').

     3) A local user name or alias.

     When _a_d_d_r_e_s_s_e_s are specified, _m_a_i_l assumes a message is being sent.  It
     reads the text of the message from standard input up to an end-of-file
     (control-d), or until it reads a line consisting of just a period. When
     either of those signals is received, _m_a_i_l passes the message text and the
     list of _a_d_d_r_e_s_s_e_s to the _s_e_n_d_m_a_i_l(1M) program for further disposition.

     If a letter is found to be undeliverable, it is returned to the sender
     with diagnostics that indicate the location and nature of the failure.
     If _m_a_i_l is interrupted during input, the file _d_e_a_d._l_e_t_t_e_r is saved to
     allow editing and resending.  _d_e_a_d._l_e_t_t_e_r is normally maintained by
     _s_e_n_d_m_a_i_l, and the interrupted message will be appended to the previous
     contents.

   RRRReeeeaaaaddddiiiinnnngggg MMMMaaaaiiiillll
     The command-line arguments that follow affect READING mail:

     ----eeee        causes mail not to be printed.  An exit value of 0 is returned
               if the user has mail; otherwise, an exit value of 1 is
               returned.
     ----hhhh        causes a window of headers to be displayed rather than the
               latest message.  The display is followed by the '????' prompt.
     ----pppp        causes all messages to be printed without prompting for
               disposition.
     ----qqqq        causes _m_a_i_l to terminate after interrupts.  Normally an
               interrupt causes only the termination of the message being
               printed.




                                                                        PPPPaaaaggggeeee 1111






MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))                                                        MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))



     ----rrrr        causes messages to be printed in first-in, first-out order.
     ----ffff_f_i_l_e    causes _m_a_i_l to use _f_i_l_e (e.g., mmmmbbbbooooxxxx) instead of the default
               _s_y_s_t_e_m _m_a_i_l_b_o_x.

     _m_a_i_l, unless otherwise influenced by command-line arguments, prints a
     user's mail messages in last-in, first-out order.  For each message, the
     user is prompted with a ????, and a line is read from standard input.  The
     following commands are available to determine the disposition of the
     message:

     <new-line>, ++++, or nnnn   Go on to next message.

     dddd, or ddddpppp              Delete message and go on to next message.

     dddd ####                   Delete message number #.  Do not go on to next
                           message.

     ddddqqqq                    Delete message and quit _m_a_i_l.

     hhhh                     Display a window of headers around current message.

     hhhh ####                   Display header of message number #.

     hhhh aaaa                   Display headers of ALL messages in the user's
                           _s_y_s_t_e_m _m_a_i_l_b_o_x.

     hhhh dddd                   Display headers of messages scheduled for deletion.

     pppp                     Print current message again.

     ----                     Print previous message.

     aaaa                     Print message that arrived during the _m_a_i_l session.

     ####                     Print message number #.

     rrrr [[[[ _u_s_e_r_s ]]]]           Reply to the sender, and other _u_s_e_r(_s), then delete
                           the message.

     ssss [ _f_i_l_e_s ]           Save message in the named _f_i_l_e_s (mmmmbbbbooooxxxx is default).

     yyyy                     Same as save.

     uuuu [[[[ #### ]]]]               Undelete message number # (default is last read).

     wwww [ _f_i_l_e_s ]           Save message, without its top-most header, in the
                           named _f_i_l_e_s (mmmmbbbbooooxxxx is default).

     mmmm [ _a_d_d_r_e_s_s_e_s ]       Mail the message to the listed _a_d_d_r_e_s_s_e_s.






                                                                        PPPPaaaaggggeeee 2222






MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))                                                        MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))



     qqqq, or ccccttttllll----dddd           Put undeleted mail back in the _s_y_s_t_e_m _m_a_i_l_b_o_x and
                           quit _m_a_i_l.

     xxxx                     Put all mail back in the _s_y_s_t_e_m _m_a_i_l_b_o_x unchanged
                           and exit _m_a_i_l.

     !!!!_c_o_m_m_a_n_d              Escape to the shell to do _c_o_m_m_a_n_d.

     ????                     Print a command summary.

     When a user logs in, the presence of mail, if any, is indicated. Also,
     notification is made if new mail arrives while using _m_a_i_l.

     The _s_y_s_t_e_m _m_a_i_l_b_o_x permissions may be manipulated to alter the function
     of _m_a_i_l.  The _o_t_h_e_r permissions of the file may be read-write, read-only,
     or neither read nor write to allow different levels of privacy.  If
     changed to other than the default, the file will be preserved even when
     empty to perpetuate the desired permissions.

NNNNOOOOTTTTEEEESSSS
     Earlier versions of _m_a_i_l implemented an ----FFFF option which was used to set
     up mail forwarding by placing special control text at the top of an empty
     system mailbox.  This option is no longer supported by _m_a_i_l in favor of
     the more convenient and general mechanism provided by the ._f_o_r_w_a_r_d file
     used by _s_e_n_d_m_a_i_l(1M).

     When sending mail, _m_a_i_l does not insert a blank line at the beginning of
     the body.  Normally this is not a problem.  However, if the first line
     has the form of a valid header line (non-whitespace text, then a colon,
     and then more text), some mail delivery agents will parse it as a header
     line, find it invalid, and omit it from the delivered mail.  When sending
     mail (particularly from programs) that might (sometimes) start with such
     a line, the problem can be avoided by making the the first line of the
     body be empty; that is, just a newline.

FFFFIIIILLLLEEEESSSS
     /etc/passwd           to identify sender and locate users
     /var/mail/_u_s_e_r        incoming mail for _u_s_e_r; i.e., the _s_y_s_t_e_m _m_a_i_l_b_o_x
     /var/mail/_u_s_e_r.lock   lock for _u_s_e_r's _s_y_s_t_e_m _m_a_i_l_b_o_x
     $HOME/mbox            saved mail
     $MAIL                 variable containing path name of the _s_y_s_t_e_m _m_a_i_l_b_o_x
     /tmp/mail*            misc. temporary files
     /var/mail/:saved      directory where temporary copies of the _s_y_s_t_e_m
                           _m_a_i_l_b_o_x are written when it is being updated
     dead.letter           file where the text of last aborted message will be
                           saved

SSSSEEEEEEEE AAAALLLLSSSSOOOO
     login(1), mail_bsd(1), rmail(1M), sendmail(1M), uux(1C), write(1),
     aliases(4).





                                                                        PPPPaaaaggggeeee 3333






MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))                                                        MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))



     Internet RFC 822 - Standard for the Format of Internet Text Messages.

BBBBUUUUGGGGSSSS
     Conditions sometimes result in a failure to remove a lock file.
     After an interrupt, the next message may not be printed; printing may be
     forced by typing a pppp.


DDDDIIIIAAAAGGGGNNNNOOOOSSSSTTTTIIIICCCCSSSS
     Upon successful completion, a value of zero is returned.  Otherwise a
     value is returned to to indicate the error:

     1        flag 'e' error

     2        file error

     3        no space

     4        cannot forward

     5        syntax error

     6        forwarding loop

     7        invalid sender

     8        invalid user

     9        too many From lines

     10       bad permissions

     11       mbox problem

     12       temporary file problem

     13       Cannot create dead.letter

     14       Unbounded forwarding

     15       cannot create lock file - XXXrs

     16       no group id of 'mail'

     17       malloc failure

     18       could not fork

     19       could not pipe






                                                                        PPPPaaaaggggeeee 4444






MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))                                                        MMMMAAAAIIIILLLL____AAAATTTTTTTT((((1111))))



     20       invoker does not own mailfile

     21       can't call sendmail




















































                                                                        PPPPaaaaggggeeee 5555